For myself I can say that I even printed out on paper all pages that seemed
to be about that.

- The genreal output optins
- Tracing options
- Shell Output Options
- etc.

and I did not understand that even there is a command like /RENDER
but that is the place where i would have expected to find it. (MY mistake ?)

One thing is true, me and - be honest 99% of all people - (IF they read
instructions) they take them
part by part when they need it.

I can however state here that this works perfect: now (and I did not expect
anything else):


********
bin\pvengine.exe  /EXIT /RENDER "D:\Dokumente und
Einstellungen\user@teop\Desktop\White space
betwen\COM\abyss_08152002_174636_87176_1_0x0-80x120a.ini"
********

--Theo
"Thorsten Froehlich" <tho### [at] trfde> schrieb im Newsbeitrag
news:3d5bbd65$1@news.povray.org...
> In article <9qanluo85j0pnd96u407t97do34eneupr3@4ax.com> , Scott Moore
> <sdm### [at] zoomcouk>  wrote:
>
> > Does this mean the docs need to be updated to mention that spaces in
> > the filename aren't allowed?
> >
> > (BTW. As I'm mentioning the docs, do all platforms build the source to
> > pvengine or povray? On Windows the .exe is pvengine - but the docs, as
> > shown above, suggest it's povray.exe - do the docs need updating for
> > this also?)
>
> The documentation is clear that it is about the command-line version of
> POV-Ray, not the GUI versions and it does refer you to the GUI version
> documentation for specifics of those versions.  Where?  Well, in the
> introduction of the command-line options in section 5 in case you missed
it.
>
> If you don't read the documentation carefully and get burned that is not a
> bug in POV-Ray but in your method of reading the documentation.  The
> suggested way to read it is from section 1 to the last section.  It is not
> recommended to use it for reference purposes only.  That way you _will_
miss
> very important details!
>
>     Thorsten

Post a reply to this message